5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
- Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-8: Application Design Tools

Database Management File Specification


Files Specifications allows you to enter information about each file.  A screen shot of the Specification display is shown below.

File Specification Screen

Records.  Used to estimate the approximate number of records for each of the design files of a new application. Remember, the numbers you enter represent the total number of records of each type for the entire application.  Using older computer systems relied on this estimate to reserve space on the system to store data.  Today this isn't as critical. 

FMS.  File Management System, specifies the access method to be used.

FMS 1 - APPX's default ISAM, known as APPXIO
FMS 2 - ACUCOBOL's Vision ISAM, on Unix systems only.
FMS 3 - Informix's C-ISAM, on Unix systems only.
FMS 4 - Sybase (Not Currently Supported)
FMS 5 - Oracle
FMS 6 - ODBC
FMS 7 - APPX/Net
FMS 8 - DB/2

Some of these interfaces are separately licensed products from their respective vendors and require additional files from APPX Software.

FMS Group.  FMS Group allows you to specify the file management group that this file belongs to. The FMS Group and the FMS reference the system defaults file in system administration, which provides default values for certain file specifications.  You may press SCAN to get a list of Valid FMS Groups. FMS Groups are maintained in System Administration, Configuration, File System Groups.  If this file is a temporary file, you may find it useful to specifically define the preferred directory for the file. APPX needs read/write/modify security clearances for anyone using temporary files.

You can also establish a unique directory using the Path field in the overlay that is presented when you press RETURN.

Use DB.  Use DB (Use Database) (optional) APPX allows multiple databases to share a single file or set of files.  If you enter a value in this field and the estimated number of records you specified for the file is zero, APPX uses (shares) the database that you specify here when referencing the file.  

Verify Struct?.  This feature is not currently implemented. Do not change its default value of "blank".

Opts.  Options will be highlighted if present.

File Attributes.  File Attributes at the file level can be used to override the FMS Group Attributes specified at the "File System Group" level.  This provides necessary information for accessing files for certain FMS Types.  Some FMS Types use the older Control String. Beginning with APPX 4.1, some FMS Types use specification based attributes.  You will be presented with the appropriate screen for the FMS Type.  The figure below illustrates the File Attributes overlay for the STREAM file.

 

File Attributes Overlay

Track Locks?  This is primarily used for debugging your programs.  If you set this to Yes, APPX records extra information for this file whenever a record is locked. There is a performance penalty when you use this option (two extra I/O operations for each successful read with hold) so you may want to apply this option selectively.

Log Profile.  Log Profile is a system dependant value that designates which Log Profile to use with this FMS group. Fill this in only if you are setting up an FMS group for logging.

Encryption Key.  Enter up to 40 characters to use as an encryption key. You can also use the 'Generate Random Key' option to have the system generate a 40 character key for you.

 

Option Path.  Path allows you to override the standard default path name that APPX automatically assigns. This is a system-specific value. It should be the physical location of the tree starting-point from which the location of the actual datafile is derived. On a non-Unix system, it could be a disk drive override. On all systems, it can be a subdirectory override.  If left blank, APPX uses the combined FMS Group and FMS values provided on the File Specifications screen to retrieve the FMS path name from the File System Groups file. If the FMS Group on the File Specifications screen is blank, APPX uses the standard values for FMS Path.

 

Optional Path Overlay

Field Overrides.  Field overrides are used by the RDBMS interfaces (Oracle, Sybase, ODBC, etc.). With field overrides an administrator can specify field level parameters to be used by the engine in communicating with the RDBMS.

 

Field Overrides Overlay

Application Design Manual                                         "Powered by Appx Software"

975

©2006 By APPX Software, Inc. All Rights Reserved